• Yes. Simple Setup. The USB Hub with the device drivers creates a separate Virtual COM port for each USB at the required speed. OpenCPN then acts as the Multiplexer when you make separate Connections for each of the virtual COM ports created. Example:
• Inateck USB3.0 3-port hub with gigabit ethernet port $20
• Bu-353-S4 GPS puck $25
• dAISy AIS Receiver $70
• Tiny Seatalk Link $150 for Raymarine Instruments (up to ST60).
• Label the ports for the devices and use those ports or you'll be redoing OpenCPN “Connections”.
• Install each device's drivers.
• or another example, Vesper AIS and RS422 NEMA instruments.
• For more about Supplementary Hardware or consult with a marine electronics service.
• A multiplexer will join multiple sources into a single output to OpenCPN. Multiplexers come in a great variety, to do many different jobs, read the specs.
• Tips for working with multiple serial sources
  • Label the hub and usb devices and always plug them into the same location once they work in Opencpn.
  • OCPN will never assign a port to a new connection by itself, you must select one from the dropdown list OR enter it yourself, for example: “COM11”.
  • To confirm which COM port is used for a USB device, open Windows Device Manager and watch what happens when the device is connected and disconnected from the USB-HUB/Splitter.
  • Then select or enter the corresponding COM port in OCPN Connections.
  • Be sure to set correct baud rate.
  • To find and use the Device Manager look here

• Simply fill in the virtual port name manually, the field is not limited to selection of the ports that were detected.

• You can add absolutely anything to the filter (Click on the “Add” button), the predefined list is there just to save you some typing for the most common message types.

1. Raspbian OS, https://github.com/OpenCPN/OpenCPN/issues/1928
2. This is an OS problem. your OS starts numbering with the first device coming up, and this is not always happen in the same sequence. The good news is you can tell your OS to give an fixed name to a fixed device, and you can use this fixed name in OpenCPN. see:
3. https://www.domoticz.com/wiki/Assign_fixed_device_name_to_USB_port
4. https://www.domoticz.com/wiki/PersistentUSBDevices
5. Or use Openplotter and its “serial” for the same purpose :)

See CF Dataport Connection problem There are some things related to serial data ports, in particular on Flatpak. * There is a bug: https://github.com/OpenCPN/OpenCPN/issues/2528- * The port must be accessible. See https://github.com/OpenCPN/OpenCPN/blob/master/LINUX_DEVICES.md, the chapter on Device Access. * Even if the port is accessible it might not be visible in the UI. Two solutions. * The first is to write the name of the device, perhaps something like /dev/ttyUSB0 in the GUI (one don't have to select from the drop-down list, it's possible to enter the device name as well) * The second is to create a device link as described in https://github.com/OpenCPN/OpenCPN/blob/master/LINUX_DEVICES.md, the chapter on Fixed Device Names. Such links are visible in the GUI

A new point Flatpak point fix has been pushed for this issue. To update the Flatpak installation do

Code:

<alt2> $ flatpak update org.openpcn.OpenCPN </alt2>

Note that despite the patch, devices must still be accessible as described in https://github.com/OpenCPN/OpenCPN/b...NUX_DEVICES.md

On Rpi I type Telnet localhost 10110 I see the stream of NMEA 0183 sentences coming from the Signalk Server. Apparently OpenCpn does not work that way.

OpenCPN does not recognize anything other than Q4 notation in the address field. “localhost” is a semi-standard shorthand notation, used on many systems and apps. In OpenCPN, Instead of “localhost”, use ip of 127.0.0.1. It is the same thing.